Generating bpel control flows

ABSTRACT

Generating Business Process Execution Language (‘BPEL’) control flows to populate a data warehouse for analysis of data of an operational system including identifying source tables in the operational system and one or more corresponding target tables in the data warehouse; creating BPEL steps to represent links between each source table in the operational system and each corresponding target table in the data warehouse; determining a sequence for the BPEL step; and adding the BPEL steps to a BPEL control flow according to the determined sequence.

RELATED APPLICATIONS

This application claims the priority benefit of U.S. application Ser.No. 11/868,472 filed Oct 6, 2007.

BACKGROUND

1. Field of the Invention

The field of the invention is data processing, or, more specifically,methods, apparatus, and products for generating Business ProcessExecution Language (‘BPEL’) control flows.

2. Description of Related Art

The development of the EDV AC computer system of 1948 is often cited asthe beginning of the computer era. Since that time, computer systemshave evolved into extremely complicated devices. Today's computers aremuch more sophisticated than early systems such as the EDVAC. Computersystems typically include a combination of hardware and softwarecomponents, application programs, operating systems, processors, buses,memory, input/output devices, and so on. As advances in semiconductorprocessing and computer architecture push the performance of thecomputer higher and higher, more sophisticated computer software hasevolved to take advantage of the higher performance of the hardware,resulting in computer systems today that are much more powerful thanjust a few years ago.

Modem businesses rely on database technology to track critical businessinformation. This information is often spread across many databasesystems. The information may, in any business activity, be modified,moved, or otherwise used. To increase efficiency in business activities,a business may from time to time examine the information in the databasesystem. To analyze information without increasing the strain on thedatabase system used for typical business activities, the informationmay be extracted, transformed, and loaded (‘ETL’) into an externalsystem, called a data warehouse, where it is analyzed. Each ETL dataflowfrom the database system to the data warehouse may be a databaseapplication program, a Sequenced Query Language script, or a batchscript. ETL performed on any database system may include many discreteETL dataflows. Currently, creating a single control flow to representthe combination of many ETL dataflows is a tedious, manual, error-prone,and time-consuming task.

SUMMARY

Methods, apparatus, and products for generating Business ProcessExecution Language (‘BPEL’) control flows to populate a data warehousefor analysis of data of an operational system are disclosed that includeidentifying source tables in the operational system and one or morecorresponding target tables in the data warehouse; creating BPEL stepsto represent links between each source table in the operational systemand each corresponding target table in the data warehouse; determining asequence for the BPEL step; and adding the BPEL steps to a BPEL controlflow according to the determined sequence.

The foregoing and other objects, features and advantages of theinvention will be apparent from the following more particulardescriptions of exemplary embodiments of the invention as illustrated inthe accompanying drawings wherein like reference numbers generallyrepresent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 sets forth a block diagram of an exemplary system that operatesgenerally for generating BPEL control flows to populate a data warehousefor analysis of data of an operational system according to embodimentsof the present invention.

FIG. 2 sets forth a block diagram of automated computing machinerycomprising an exemplary computer useful in for generating BPEL controlflows to populate a data warehouse for analysis of data of anoperational system according to embodiments of the present invention.

FIG. 3 sets forth a flow chart illustrating an exemplary method forgenerating BPEL control flows to populate a data warehouse for analysisof data of an operational system according to embodiments of the presentinvention.

FIG. 4 sets forth a flow chart illustrating a further exemplary methodfor generating BPEL control flows to populate a data warehouse foranalysis of data of an operational system according to embodiments ofthe present invention.

FIG. 5 sets forth a flow chart illustrating a further exemplary methodfor generating BPEL control flows to populate a data warehouse foranalysis of data of an operational system according to embodiments ofthe present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Exemplary methods, apparatus, and products for generating BPEL controlflows in accordance with the present invention are described withreference to the accompanying drawings, beginning with FIG. 1. FIG. 1sets forth a block diagram of an exemplary system that operatesgenerally for generating BPEL control flows to populate a data warehousefor analysis of data of an operational system according to embodimentsof the present invention.

The system of FIG. 1 includes an operational system (322). Anoperational system is a system that includes data that is used,transformed, or moved, during typical activities of a business. Anoperational system may include any number of data structures, such asfor example, databases that include tables. Databases in an operationalsystem may be organized according to any number of database modelsincluding, relational, hierarchical, network or other models as willoccur to those of skill in the art.

Businesses may analyze data in the operational system (322) to increaseefficiency of the operational system (322). To analyze the data withoutincreasing the strain on the operational system caused by examining thedata in the operational system, the data is transferred to an externalsystem, a data warehouse. A data warehouse is a repository of ahistorical data. Data in a data warehouse is typically:

-   -   subject-oriented, in that the data relating to the same        real-world event or object is linked together;    -   time-variant, in that the changes to the data in the database        are tracked and recorded so that reports can be produced showing        changes over time;    -   non-volatile, in that the data is typically not over-written or        deleted; and    -   integrated, in that the data warehouse contains data from most        or all organization's operational activities.

The process of populating such a data warehouse is typically describedas ETL—Extract, Transform, and Load. ETL is a process that involvesextracting data from sources, transforming the data, and loading thedata into the data warehouse.

The operational system (322) of FIG. 1 includes several source tables(302). A source table is a table in the operational system that containsdata that is extracted from the operational system, transformed, andloaded into a data warehouse (324) for analysis. The data warehouse(324) of FIG. 1 includes several target tables (304). A target table isa table in which data from a source table in the operational system isloaded. When data is loaded into the target table the data may beanalyzed.

The system of FIG. 1 also includes several links (306, 308, and 310).Each link represents an ETL action, that is, an extraction,transformation, and loading of data during the population of a datawarehouse. A link may represent, for example, that during population ofa data warehouse, a column in a source table is copied and loaded into atarget table in the data warehouse. A link may also represent, forexample, that during population of a data warehouse, a particular recordof source table is extracted, summed with another record from anothersource table, and loaded into a target table in the data warehouse.

As mentioned above the system of FIG. 1 operates generally forgenerating BPEL control flows to populate a data warehouse for analysisof data of an operational system according to embodiments of the presentinvention. Business Process Execution Language (‘BPEL’) is based uponextensible markup language (‘XML’) and is used for the formalspecification of business processes and business interaction protocols.A BPEL control flow is a representation of one or more businessesprocesses that includes a set of sequenced BPEL activities that arecarried out during the execution of the one or more business processes.

The system of FIG. 1 includes a BPEL control flow creator (125), amodule of computer program instructions. The exemplary BPEL control flowcreator (125) of FIG. 1 is capable of identifying source tables (302) inthe operational system (322) and one or more corresponding target tables(304) in the data warehouse. The exemplary BPEL control flow creator(125) of FIG. 1 is also capable of creating BPEL steps (328) torepresent links (306, 308, 310, 320) between each source table (302) inthe operational system (322) and each corresponding target table (304)in the data warehouse (324). The exemplary BPEL control flow creator(125) of FIG. 1 is also capable of determining a sequence (344) for theBPEL steps including: determining relationships among source tables inthe operational system; determining relationships among target tables inthe data warehouse; and applying a BPEL policy that includes therelationships among source tables in the operational system andrelationships among target tables in the data warehouse. The exemplaryBPEL control flow creator (125) of FIG. 1 is also capable of adding theBPEL steps (328) to a BPEL control flow (348) according to thedetermined sequence (344).

Generating BPEL control flows in accordance with the present inventionis generally implemented with computers, that is, with automatedcomputing machinery. In the system of FIG. 1, for example, theoperational system (322), data warehouse (324), and BPEL control flowcreator (125) are implemented to some extent at least as computers. Forfurther explanation, therefore, FIG. 2 sets forth a block diagram ofautomated computing machinery comprising an exemplary computer (152)useful in for generating BPEL control flows to populate a data warehousefor analysis of data of an operational system according to embodimentsof the present invention. The computer (152) of FIG. 2 includes at leastone computer processor (156) or ‘CPU’ as well as random access memory(168) (‘RAM’) which is connected through a high speed memory bus (166)and bus adapter (158) to processor (156) and to other components of thecomputer (152).

Stored in RAM (168) is a BPEL control flow creator (125), a module ofcomputer program instructions improved for generating BPEL control flowsaccording to embodiments of the present invention. The BPEL control flowcreator (125) is capable of identifying source tables in the operationalsystem (322) and one or more corresponding target tables in the datawarehouse (324) and creating BPEL steps (328) to represent links betweeneach source table in the operational system (322) and each correspondingtarget table in the data warehouse (324). The BPEL control flow creator(125) of FIG. 2 is also capable of determining a sequence (344) for theBPEL steps (328) including determining relationships among source tablesin the operational system (322), determining relationships among targettables in the data warehouse (324), applying a BPEL policy that includesthe relationships among source tables in the operational system andrelationships among target tables in the data warehouse. The BPELcontrol flow creator (125) of FIG. 2 is also capable of adding the BPELsteps (328) to a BPEL control flow according to the determined sequence(344).

Also stored in RAM (168) is an operating system (154). Operating systemsuseful generating BPEL control flows according to embodiments of thepresent invention include UNIX™, Linux™, Microsoft XP™, AIX™, IBM'si5/OS™, and others as will occur to those of skill in the art. Theoperating system (154), BPEL control flow creator (125), BEP steps(328), and sequence (344) in the example of FIG. 2 are shown in RAM(168), but many components of such software typically are stored innon-volatile memory also, such as, for example, on a disk drive (170).

The computer (152) of FIG. 2 includes disk drive adapter (172) coupledthrough expansion bus (160) and bus adapter (158) to processor (156) andother components of the computer (152). Disk drive adapter (172)connects non-volatile data storage to the computer (152) in the form ofdisk drive (170). Disk drive adapters useful in computers for generatingBPEL control flows according to embodiments of the present inventioninclude Integrated Drive Electronics (‘IDE’) adapters, Small ComputerSystem Interface (‘SCSI’) adapters, and others as will occur to those ofskill in the art. Non-volatile computer memory also may be implementedfor as an optical disk drive, electrically erasable programmableread-only memory (so-called ‘EEPROM’ or ‘Flash’ memory), RAM drives, andso on, as will occur to those of skill in the art.

The example computer (152) of FIG. 2 includes one or more input/output(‘I/O’) adapters (178). I/O adapters implement user-orientedinput/output through, for example, software drivers and computerhardware for controlling output to display devices such as computerdisplay screens, as well as user input from user input devices (181)such as keyboards and mice. The example computer (152) of FIG. 2includes a video adapter (209), which is an example of an I/O adapterspecially designed for graphic output to a display device (180) such asa display screen or computer monitor. Video adapter (209) is connectedto processor (156) through a high speed video bus (164), bus adapter(158), and the front side bus (162), which is also a high speed bus.

The exemplary computer (152) of FIG. 2 includes a communications adapter(167) for data communications with other computers (182) and for datacommunications with a data communications network (100). Such datacommunications may be carried out serially through RS-232 connections,through external buses such as a Universal Serial Bus (‘USB’), throughdata communications data communications networks such as IP datacommunications networks, and in other ways as will occur to those ofskill in the art. Communications adapters implement the hardware levelof data communications through which one computer sends datacommunications to another computer, directly or through a datacommunications network. Examples of communications adapters useful forgenerating BPEL control flows according to embodiments of the presentinvention include modems for wired dial-up communications, Ethernet(IEEE 802.3) adapters for wired data communications networkcommunications, and 802.11 adapters for wireless data communicationsnetwork communications.

For further explanation, FIG. 3 sets forth a flow chart illustrating anexemplary method for generating BPEL control flows to populate a datawarehouse for analysis of data of an operational system according toembodiments of the present invention. The method of FIG. 3 includesidentifying (312) source tables (302) in the operational system (322)and one or more corresponding target tables (304) in the data warehouse(324). Identifying (312) source tables (302) in the operational system(322) and one or more corresponding target tables (304) may be carriedout by inferring, from actions specified in an Extraction,Transformation, and Load (‘ETL’) control flow, source tables in theoperational system and one or more corresponding target tables in thedata warehouse. Existing operational systems may have ETL control flowsassociated with the system such that upon implementation of the presentinvention, the ETL control flows may be used to identify source andtarget tables. Identifying (312) source tables (302) in the operationalsystem (322) and one or more corresponding target tables (304) may alsobe carried out by retrieving metadata that describes the source andtarget tables or receiving a specification of the source and targettables from a system administrator.

The method of FIG. 3 also includes creating (326) BPEL steps (328) torepresent links (306, 308, 310, 320) between each source table (302) inthe operational system (322) and each corresponding target table (304)in the data warehouse (324). A BPEL step is a place holder for a userassigned BPEL action. A BPEL action may include an ETL specificactivity, a call to a Web service, or some other action useful inpopulating a data warehouse for analysis.

Creating (326) BPEL steps (328) to represent links (306, 308, 310, 320)between each source table (302) in the operational system (322) and eachcorresponding target table (304) in the data warehouse (324) may becarried out by implementing a placeholder associated with anidentification of the target and source table connected by the link. Aplaceholder may be implemented as an element in an XML markup document.Consider for example, the following exemplary XML pseudocode:

<step id= “129309”> <sourceTable id = “OperationalSystem\CustomerInfo”><column id = “CustomerN arne”> </column> </sourceTable > <targetTable id= “DataWarehouse\CustomerInfo”> <column id = “CustomerN arne”> </column></targetTable> </step>

The exemplary XML above includes a <step> tag. The <step> tag identifiesa placeholder for a user assigned BPEL action. The <step> tag aboveidentifies the BPEL step as step number 129309. The step number is anumber that uniquely identifies a BPEL step. In this example the stepnumber does not identify the sequence in which the BPEL step is executedin a BPEL control flow.

The exemplary XML above also includes a <sourceTable> tag. The<sourceTable> tag identifies the source table from which data isextracted during population of the data warehouse. In this example, thesource table is identified as Operational System\CustomerInfo.

The exemplary XML above also includes a <column> tag. The <column> tagidentifies the column of data that is to be extracted from the sourcetable during population of the data warehouse. In this example, thecolumn of data that is to be extracted from the source table is the“CustomerName” column.

The exemplary XML above also includes a <targetTable> tag. The<targetTable> tag identifies the target table that is loaded duringpopulation of the data warehouse. In this example, the target table isidentified as DataWarehouse\CustomerInfo.

The exemplary XML above also includes a <column> tag for the targettable. The <column> tag identifies the column of data in the targettable that is to be loaded during population of the data warehouse. Inthis example, the column of data that is to be loaded during populationof the data warehouse is the “CustomerName” column in the target table.

The method of FIG. 3 also includes determining (320) a sequence (344)for the BPEL steps (328). In the method of FIG. 3, determining (320) asequence (344) for the BPEL steps (328) is carried out by determining(332) relationships among source tables (302) in the operational system(322); determining (334) relationships among target tables (304) in thedata warehouse (324); and applying (336) a BPEL policy (338) thatincludes the relationships (340) among source tables in the operationalsystem (322) and relationships (342) among target tables in the datawarehouse. During the population of a data warehouse for analysis ofdata in an operational system, the order of ETL actions is highlydependent upon the relationship among tables in the operational system322 and data warehouse 324.

Determining (332) relationships among source tables (302) in theoperational system (322) may be carried out by retrieving metadatadescribing the source tables in the operational system. Such metadatamay explicitly describe the relationships among the source tables.Determining (332) relationships among source tables (302) in theoperational system (322) may also include inferring the relationshipsfrom the operational system. Relationships among tables may be inferredby creating a profile of the system. Database profiling tools create aprofile of a database by identifying foreign and primary keys, foreignand primary tables, identifying a database schema that defines thestructure of the database, monitoring movement, insertion, deletion, andtransformation of data within the database, identifying names of tablesin the database, and in other ways as will occur to those of skill inthe art.

Determining (334) relationships among target tables (304) in the datawarehouse (324) may be carried out in a manner similar to that ofdetermining relationships among source tables in the operational system.Determining (334) relationships among target tables (304) in the datawarehouse (324) may be carried out by retrieving metadata describing thetarget tables in the data warehouse or by inferring the relationshipsfrom the data warehouse.

The method of FIG. 3 also includes adding (346) the BPEL steps (328) toa BPEL control flow (348) according to the determined sequence (344).Adding (346) the BPEL steps (328) to a BPEL control flow (348) accordingto the determined sequence (344) may be carried out by inserting theBPEL steps into a markup document according to the determined sequence.Consider, for example, the following exemplary XML code:

<flow name= “PreControlFlowExample”> <step id = “129309”> <sourceTableid=“OperationalSystem\CustomerInfo”></sourceTable> <targetTable id =“Data Warehouse\CustomerInfo”></targetTable> </step> <step id =“129420”> <sourceTable id =“OperationalSystem\ProductInfo”></sourceTable > <targetTable id = “DataWarehouse\ProductInfo”></targetTable> </step> </flow>

This exemplary XML is an example of a pre-BPEL control flow havingseveral steps in a determined sequence which may be converted into aBPEL control flow. As explained above, a BPEL step is not a BPEL actionthat may be carried out, but instead is a placeholder for such anaction. To convert the exemplary pre-BPEL control flow to a BPEL controlflow, a user may assign specific BPEL actions for each step. BPELactions may include an ETL specific activity, a call to a Web service,or some other action useful in populating a data warehouse for analysis.

The exemplary XML above includes a <flow> tag that identifies thepre-BPEL control flow. In this example the <flow> tag has a nameattribute identifying the control flow as, “PreControlFlowExample.”

The exemplary XML above also includes a <step> tag having anidentification of 129309. In this example, step 129309 is the first BPELstep in the determined sequence of BPEL steps for the exemplary pre-BPELcontrol flow. This exemplary step includes a <source Table> tag thatidentifies the source table from which data is extracted duringpopulation of a data warehouse. In this example, the source table isidentified as OperationalSystem\CustomerInfo. This exemplary step alsoincludes a <targetTable> tag that identifies the target table that isloaded during population of the data warehouse. In this example, thetarget table is identified as Data Warehouse\CustomerInfo.

The exemplary XML above also includes a <step> tag having anidentification of 129420. In this example, step 129420 is the secondBPEL step in the determined sequence of BPEL steps for the exemplarypre-BPEL control flow. This exemplary step includes a <source Table> tagthat identifies the source table from which data is extracted duringpopulation of a data warehouse. In this example, the source table isidentified as OperationalSystem\ProductInfo. This exemplary step alsoincludes a <targetTable> tag that identifies the target table that isloaded during population of the data warehouse. In this example, thetarget table is identified as Data Warehouse\ProductInfo.

For further explanation, FIG. 4 sets forth a flow chart illustrating afurther exemplary method for generating BPEL control flows to populate adata warehouse for analysis of data of an operational system accordingto embodiments of the present invention. The method of FIG. 4 is similarto the method of FIG. 3 in that the method of FIG. 4 includesidentifying (312) source tables (302) in the operational system (322)and one or more corresponding target tables (304) in the data warehouse(324); creating (326) BPEL steps (328) to represent links (306, 308,310, 320) between each source table (302) in the operational system(322) and each corresponding target table (304) in the data warehouse(324); determining (320) a sequence (344) for the BPEL steps (328); andadding (346) the BPEL steps (328) to a BPEL control flow (348) accordingto the determined sequence (344).

The method of FIG. 4 differs from the method of FIG. 3, however, inthat, in the method of FIG. 4 determining (320) a sequence (344) for theBPEL steps (328) includes determining (402) which BPEL steps (328) toexecute in parallel and assigning (404) the BPEL steps (328) to executein parallel to a same sequence number (408). Assigning (404) the BPELsteps (328) to execute in parallel to a same sequence number (408) maybe carried out by associating an identification of each BPEL step with asequence number. In the method of FIG. 4, for example, the sequence(344) is represented as a table that associates BPEL stepidentifications (406) and sequence numbers (408). The columnrepresenting BPEL step identifications (406) includes three BPEL stepsidentified as 10293, 10644, and 10743. The column representing sequencenumbers (408) includes a sequence number (408) for each BPEL stepidentification. The sequence number associated with the BPEL stepidentification 10293 is 1, the sequence number associated with the BPELstep identification 10644 is 1, and the sequence number associated withthe BPEL step identification 10743 is 2. BPEL steps having the samesequence number represent ETL actions that may be carried out inparallel during population of a data warehouse. In this example, steps10644 and 10743 represent actions that may be carried out in parallel.

The method of FIG. 4 also differs from the method of FIG. 3 in that, inthe method of FIG. 4 adding (346) the BPEL steps (328) to a BPEL controlflow (348) according to the determined sequence (344) includes creating(410) one or more parallel containers (412) for the BPEL steps (328)having the same sequence number (408); and adding (414) the BPEL steps(328) having the same sequence number (408) to a same parallelcontainer.

A parallel container is a portion of a BPEL control flow that representsactions that may be carried out in parallel during the population of thedata warehouse. Creating (410) one or more parallel containers (412) forthe BPEL steps (328) having the same sequence number (408) may becarried out by creating for each step having the same sequence number, asequence element in a pre-BPEL control flow markup language document andadding (414) the BPEL steps (328) having the same sequence number (408)to a same parallel container may be carried out by inserting those BPELsteps with the same sequence number into their corresponding sequenceelements in the pre-BPEL control flow. Consider as an example, thefollowing XML code:

<flow> <sequence> <step id = “129309”> </step> <sequence> <step id =“10103”> </step> </sequence> <sequence> <step id= “10104”></step> <stepid= “10250”></step> </sequence> </sequence> <sequence> <step id =“129420”></step> </sequence> </flow>

This exemplary XML is an example of a pre-BPEL control flow havingseveral parallel steps which may be converted into a BPEL control flow.As explained above, a BPEL step is not a BPEL action that may be carriedout, but instead is a placeholder for such an action. To convert theexemplary pre-BPEL control flow to a BPEL control flow, a user mayassign specific BPEL actions for each step. BPEL actions may include anETL specific activity, a call to a Web service, or some other actionuseful in populating a data warehouse for analysis.

In the exemplary XML above the pre-BPEL control flow includes a<sequence> element that identifies parallel BPEL steps. BPEL stepsincluded in sequence elements of the same hierarchical level in thepre-BPEL control flow are parallel BPEL steps. There are five BPEL stepsrepresented in the exemplary XML above including steps 129309, 10103,10104, 10250, 102940. Steps 129309 and 129420 are parallel BPEL steps.Within step 129309 are three other BPEL steps. BPEL step 10103 isparallel to steps 10104 and 10250. Only steps having identificationnumbers are shown in the above example for clarity but readers of skillin the art will recognize that such a pre-BPEL control flow may alsoinclude other information such as, for example, target and source tablesfor each BPEL step.

For further explanation, FIG. 5 sets forth a flow chart illustrating afurther exemplary method for generating BPEL control flows to populate adata warehouse for analysis of data of an operational system accordingto embodiments of the present invention. The method of FIG. 5 is similarto the method of FIG. 3 in that the method of FIG. 5 includesidentifying (312) source tables (302) in the operational system (322)and one or more corresponding target tables (304) in the data warehouse(324); creating (326) BPEL steps (328) to represent links (306, 308,310, 320) between each source table (302) in the operational system(322) and each corresponding target table (304) in the data warehouse(324); determining (320) a sequence (344) for the BPEL steps (328); andadding (346) the BPEL steps (328) to a BPEL control flow (348) accordingto the determined sequence (344).

The method of FIG. 5 differs from the method of FIG. 3, however, in thatthe method of FIG. 5 includes identifying (514) source tables (502,506)in the data warehouse (324) and one or more additional correspondingtarget tables (506, 504) in the data warehouse (324). From time to timeduring the population of a data warehouse for analysis of data in anoperational system data already loaded into the data warehouse may beextracted, transformed, and loaded into other tables within the datawarehouse. Identifying (514) source tables (502,506) in the datawarehouse (324) and one or more additional corresponding target tables(506, 504) in the data warehouse (324) may be carried out by inferringthe source and target tables from actions specified in an ETL controlflow, retrieving metadata that describes the source and target tables,or receiving a specification of the source and target tables from asystem administrator.

The method of FIG. 5 also differs from the method of FIG. 3 in that themethod of FIG. 5 includes creating (516) additional BPEL steps (518) torepresent links (508, 510512) between each source table (502,506) in thedata warehouse (324) and each additional corresponding target table(504) in the data warehouse. As mentioned above, creating a BPEL stepmay be carried out by implementing a placeholder associated with anidentification of the target and source table connected by the link theBPEL step represents. A placeholder may be implemented as an element inan BPEL control flow markup document.

The method of FIG. 5 also differs from the method of FIG. 3 in that, inthe method of FIG. 5 determining (330) a sequence (344) for the BPELsteps (328) includes determining (520) a sequence (524) for theadditional BPEL steps (518), and adding (346) the BPEL steps (328) tothe BPEL control flow (348) according to the determined sequence (344)includes adding (522) the additional BPEL steps (518) to the BPELcontrol flow (348) according to the determined sequence (524) for theadditional BPEL steps (518). As mentioned above, adding BPEL steps tothe BPEL control flow may be carried out by inserting the BPEL stepsinto a markup document according to the determined sequence.

Exemplary embodiments of the present invention are described largely inthe context of a fully functional computer system for generating BPELcontrol flows. Readers of skill in the art will recognize, however, thatthe present invention also may be embodied in a computer program productdisposed on signal bearing media for use with any suitable dataprocessing system. Such signal bearing media may be transmission mediaor recordable media for machine-readable information, including magneticmedia, optical media, or other suitable media. Examples of recordablemedia include magnetic disks in hard drives or diskettes, compact disksfor optical drives, magnetic tape, and others as will occur to those ofskill in the art. Examples of transmission media include telephonenetworks for voice communications and digital data communicationsnetworks such as, for example, Ethernets™ and networks that communicatewith the Internet Protocol and the World Wide Web as well as wirelesstransmission media such as, for example, networks implemented accordingto the IEEE 802.11 family of specifications. Persons skilled in the artwill immediately recognize that any computer system having suitableprogramming means will be capable of executing the steps of the methodof the invention as embodied in a program product. Persons skilled inthe art will recognize immediately that, although some of the exemplaryembodiments described in this specification are oriented to softwareinstalled and executing on computer hardware, nevertheless, alternativeembodiments implemented as firmware or as hardware are well within thescope of the present invention.

It will be understood from the foregoing description that modificationsand changes may be made in various embodiments of the present inventionwithout departing from its true spirit. The descriptions in thisspecification are for purposes of illustration only and are not to beconstrued in a limiting sense. The scope of the present invention islimited only by the language of the following claims.

1. A method for generating Business Process Execution Language (‘BPEL’)control flows to populate a data warehouse for analysis of data of anoperational system, the method comprising: identifying source tables inthe operational system and one or more corresponding target tables inthe data warehouse; creating BPEL steps to represent links between eachsource table in the operational system and each corresponding targettable in the data warehouse; determining a sequence for the BPEL stepsincluding: determining which BPEL steps to execute in parallel andassigning the BPEL steps to execute in parallel to a same sequencenumber; determining relationships among source tables in the operationalsystem; determining relationships among target tables in the datawarehouse; and applying a BPEL policy that includes the relationshipsamong source tables in the operational system and relationships amongtarget tables in the data warehouse; and adding the BPEL steps to a BPELcontrol flow according to the determined sequence.
 2. The method ofclaim 1 wherein: adding the BPEL steps to the BPEL control flowaccording to the determined sequence further comprises: creating one ormore parallel containers for the BPEL steps having the same sequencenumber; and adding the BPEL steps having the same sequence number to asame parallel container.
 3. The method of claim 1 wherein: determiningrelationships among source tables in the operational system furthercomprises retrieving metadata describing the source tables in theoperational system; and determining relationships among target tables inthe data warehouse further comprises retrieving metadata describing thetarget tables in the data warehouse.
 4. The method of claim 1 wherein:determining relationships among source tables in the operational systemfurther comprises inferring the relationships from the operationalsystem; and determining relationships among target tables in the datawarehouse further comprises inferring the relationships from the datawarehouse.
 5. The method of claim 1 wherein identifying source tables inthe operational system and one or more corresponding target tables inthe data warehouse further comprises: inferring, from actions specifiedin an Extraction, Transformation, and Load (‘ETL’) control flow, sourcetables in the operational system and one or more corresponding targettables in the data warehouse.
 6. An apparatus for generating BusinessProcess Execution Language (‘BPEL’) control flows to populate a datawarehouse for analysis of data of an operational system, the apparatuscomprising a computer processor, a computer memory operatively coupledto the computer processor, the computer memory having disposed within itcomputer program instructions that when executed by the computerprocessor cause the computer processor to: identify source tables in theoperational system and one or more corresponding target tables in thedata warehouse; create BPEL steps to represent links between each sourcetable in the operational system and each corresponding target table inthe data warehouse; determine a sequence for the BPEL steps including:determine which BPEL steps to execute in parallel and assigning the BPELsteps to execute in parallel to a same sequence number; determinerelationships among source tables in the operational system; determinerelationships among target tables in the data warehouse; and apply aBPEL policy that includes the relationships among source tables in theoperational system and relationships among target tables in the datawarehouse; and add the BPEL steps to a BPEL control flow according tothe determined sequence.
 7. The apparatus of claim 6 wherein: thecomputer program instructions that when executed by the computerprocessor cause the computer processor to determine a sequence for theBPEL steps further comprises computer program instructions that whenexecuted by the computer processor cause the computer processor to: addthe BPEL steps to the BPEL control flow according to the determinedsequence further comprises: create one or more parallel containers forthe BPEL steps having the same sequence number; and add the BPEL stepshaving the same sequence number to a same parallel container.
 8. Theapparatus of claim 6 wherein: the computer program instructions thatwhen executed by the computer processor cause the computer processor todetermine relationships among source tables in the operational systemfurther comprises computer program instructions that when executed bythe computer processor cause the computer processor to retrieve metadatadescribing the source tables in the operational system; and the computerprogram instructions that when executed by the computer processor causethe computer processor to determine relationships among target tables inthe data warehouse further comprises computer program instructions thatwhen executed by the computer processor cause the computer processor toretrieve metadata describing the target tables in the data warehouse. 9.The apparatus of claim 6 wherein: the computer program instructions thatwhen executed by the computer processor cause the computer processor todetermine relationships among source tables in the operational systemfurther comprises computer program instructions that when executed bythe computer processor cause the computer processor to infer therelationships from the operational system; and the computer programinstructions that when executed by the computer processor cause thecomputer processor to determine relationships among target tables in thedata warehouse further comprises computer program instructions that whenexecuted by the computer processor cause the computer processor to inferthe relationships from the data warehouse.
 10. The apparatus of claim 6wherein the computer program instructions that when executed by thecomputer processor cause the computer processor to identify sourcetables in the operational system and one or more corresponding targettables in the data warehouse further comprises: computer programinstructions that when executed by the computer processor cause thecomputer processor to infer, from actions specified in an Extraction,Transformation, and Load ('ETL') control flow, source tables in theoperational system and one or more corresponding target tables in thedata warehouse.
 11. A computer program product for generating BusinessProcess Execution Language ('BPEL') control flows to populate a datawarehouse for analysis of data of an operational system, the computerprogram product comprising: a computer readable, recordable, nontransmission medium having computer readable program code embodiedtherewith, the computer readable program code comprising: computerreadable program code configured to identify source tables in theoperational system and one or more corresponding target tables in thedata warehouse; computer readable program code configured to create BPELsteps to represent links between each source table in the operationalsystem and each corresponding target table in the data warehouse;computer readable program code configured to determine a sequence forthe BPEL steps including: computer readable program code configured todetermine which BPEL steps to execute in parallel and assigning the BPELsteps to execute in parallel to a same sequence number; computerreadable program code configured to determine relationships among sourcetables in the operational system; computer readable program codeconfigured to determine relationships among target tables in the datawarehouse; and computer readable program code configured to apply a BPELpolicy that includes the relationships among source tables in theoperational system and relationships among target tables in the datawarehouse; and computer readable program code configured to add the BPELsteps to a BPEL control flow according to the determined sequence. 12.The computer program product of claim 11 wherein: the computer readableprogram code configured to determine a sequence for the BPEL stepsfurther comprises: computer readable program code configured to add theBPEL steps to the BPEL control flow according to the determined sequencefurther comprises: computer readable program code configured to createone or more parallel containers for the BPEL steps having the samesequence number; and computer readable program code configured to addthe BPEL steps having the same sequence number to a same parallelcontainer.
 13. The computer program product of claim 11 wherein: thecomputer readable program code configured to determine relationshipsamong source tables in the operational system further comprises computerreadable program code configured to retrieve metadata describing thesource tables in the operational system; and the computer readableprogram code configured to determine relationships among target tablesin the data warehouse further comprises computer readable program codeconfigured to retrieve metadata describing the target tables in the datawarehouse.
 14. The computer program product of claim 11 wherein: thecomputer readable program code configured to determine relationshipsamong source tables in the operational system further comprises computerreadable program code configured to infer the relationships from theoperational system; and the computer readable program code configured todetermine relationships among target tables in the data warehousefurther comprises computer readable program code configured to infer therelationships from the data warehouse.
 15. The computer program productof claim 11 wherein the computer readable program code configured toidentify source tables in the operational system and one or morecorresponding target tables in the data warehouse further comprises:computer readable program code configured to infer, from actionspecified in an Extraction, Transformation, and Load ('ETL') controlflow, source tables in the operational system and one or morecorresponding target tables in the data warehouse.